Merge commits from main make the PR history harder to review. Please rebase your branch on top of the latest main instead, then update the PR with the rebased commits.

• frontend: Add disk/storage column to nodes list view — Only one file changed inside frontend/; add a sub-area so it's clear what was touched (e.g. frontend: ComponentName: description).

• Use atomic commits focused on a single change.
• Use the title format <area>: <Description of changes> — description must start with a capital letter.
• Keep the title under 72 characters (soft requirement).
• Explain the intention and why the change is needed.
• Make commit titles meaningful and describe what changed.
• Do not add code that a later commit rewrites; squash or reorder commits instead.
• Do not include Fixes #NN in commit messages.

Good examples:

• frontend: HomeButton: Fix so it navigates to home
• backend: config: Add enable-dynamic-clusters flag

• frontend: — Missing area: description prefix — e.g. frontend: HomeButton: Fix so it navigates to home or backend: config: Add enable-dynamic-clusters flag.

• Use atomic commits focused on a single change.
• Use the title format <area>: <Description of changes> — description must start with a capital letter.
• Keep the title under 72 characters (soft requirement).
• Explain the intention and why the change is needed.
• Make commit titles meaningful and describe what changed.
• Do not add code that a later commit rewrites; squash or reorder commits instead.
• Do not include Fixes #NN in commit messages.

Good examples:

• frontend: HomeButton: Fix so it navigates to home
• backend: config: Add enable-dynamic-clusters flag

frontend/src/components/node/List.tsx:89

• The new disk column is only covered by a snapshot where both fixture nodes render an empty disk cell (the story helper has empty/missing ephemeral storage values), so the non-zero StorageBarChart path, tooltip contents, and numeric disk sorting are not exercised. Please add node fixture data or a focused test with non-zero ephemeral-storage capacity/allocatable values.

          render: node => <StorageBarChart node={node} />,

frontend/src/components/node/Charts.tsx:107

• Capacity is already localized in the glossary namespace (for example frontend/src/i18n/locales/es/glossary.json:237), while the newly added translation|Capacity entries are empty outside English and fall back to English. Using the translation namespace here makes this tooltip partially untranslated for non-English users; use the existing glossary key/namespace instead of duplicating the term.

        {t('translation|Allocatable')}: {allocatableInfo.value}
        {allocatableInfo.unit} / {t('translation|Capacity')}: {capacityInfo.value}
        {capacityInfo.unit} ({getPercentStr(allocatable, capacity)})